Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(material/schematics): add migration to switch to the new theming API #22304

Merged
merged 1 commit into from
Mar 27, 2021

Conversation

crisbeto
Copy link
Member

Adds an ng-generate schematic that will switch over existing stylesheets to the new @use-based API. Furthermore, the migration code is set up in a way that should allow us to run it in g3 if necessary.

@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround merge safe target: major This PR is targeted for the next major release labels Mar 21, 2021
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 21, 2021
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me (given the amount of context I have). Jeremy's comment for Copybara sounds reasonable to me.

@jelbourn
Copy link
Member

I think that's okay for now- we'll see how rollout goes and whether we need to do anything special for now-really-private APIs.

@crisbeto crisbeto force-pushed the theming-schematic branch from 9c75771 to d95e8d6 Compare March 23, 2021 19:45
@crisbeto
Copy link
Member Author

@jelbourn I've expanded the migration to handle any @import from angular/material and angular/cdk, as well as any @use.

@crisbeto crisbeto force-pushed the theming-schematic branch from d95e8d6 to ae1c4e9 Compare March 23, 2021 19:48
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good overall, just one main comment about identifying @use namespaces

… API

Adds an `ng-generate` schematic that will switch over existing stylesheets to the new `@use`-based API. Furthermore, the migration code is set up in a way that should allow us to run it in g3 if necessary.
@crisbeto crisbeto force-pushed the theming-schematic branch from ae1c4e9 to 517cf91 Compare March 24, 2021 20:39
@crisbeto
Copy link
Member Author

I've reworked it based on the latest set of feedback.

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, masterful

@jelbourn jelbourn added the action: merge The PR is ready for merge by the caretaker label Mar 24, 2021
@wagnermaciel wagnermaciel merged commit 183c59f into angular:master Mar 27, 2021
crisbeto added a commit to crisbeto/material2 that referenced this pull request Mar 28, 2021
This is follow-up from the PR that introduced the theming API migration (angular#22304 (comment)). It renames a few variables in the CDK to align them with the new API.
wagnermaciel pushed a commit that referenced this pull request Mar 30, 2021
This is follow-up from the PR that introduced the theming API migration (#22304 (comment)). It renames a few variables in the CDK to align them with the new API.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Apr 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P2 The issue is important to a large percentage of users, with a workaround target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants